System and method for the automated analysis of performance data

ABSTRACT

A method and system for automating the analysis of performance data includes an analysis system automatically analyzing a plurality of performance data sets, a task engine, and a score engine. The task engine allows for the matching of each performance data set with an assigned task for each performance data set and the retrieval of a correct key sequence for each performance data set. The score engine compares the correct key sequence with a recorded key sequence of the performance data set to determine if the assigned task is successfully accomplished. The score engine further calculates one or more response times for each performance data set. The automated analysis of performance data allows for a cost savings, more efficient use of time, and more reliable and consistent performance data analysis results.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 10/217,863, filed Aug. 13, 2002, by Scott H. Mills et al. and entitled “System and Method for the Automated Analysis of Performance Data”, now U.S. Pat. No. ______.

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to information processing and management, and more specifically relates to a method and system for the automated analysis of performance data.

BACKGROUND OF THE INVENTION

Every year, companies typically receive numerous telephone calls from customers seeking assistance with particular tasks. The customers often speak with customer service representatives (CSR) to complete their tasks. But because of the cost associated with CSR time, companies are switching over to automated systems such as interactive voice response (IVR) systems where IVR systems answer the customer phone calls and direct the customer phone calls to the correct service center. The IVR systems allow customers to complete their tasks without the assistance of a CSR. In order to maintain a high level of customer satisfaction, an IVR system must be designed so that customers can easily navigate the various menus and accomplish their tasks without spending too much time on the telephone and becoming frustrated and unsatisfied with the company and its services. Therefore, companies must design and continually test, update, and improve the IVR systems including the IVR menus so that the IVR systems function efficiently so that customers remain satisfied with the level of customer service.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:

FIG. 1 depicts a block diagram of a system for automating the analysis of performance data;

FIG. 2 illustrates an example graphical user interface;

FIG. 3 depicts an example log file including performance data; and

FIG. 4 illustrates a flow diagram of a method for the automated analysis of performance data.

DETAILED DESCRIPTION OF THE INVENTION

Preferred embodiments of the present invention are illustrated in the figures, like numerals being used to refer to like and corresponding parts of the various drawings.

Many companies that have customer service programs and/or call centers, such as telephone companies, Internet service providers, and credit card companies, typically have automated systems such as interactive voice response (IVR) systems that answer and direct customer phone calls when a customer calls seeking assistance for a particular task such as to change an address or inquire about payment of a bill. If a customer does not reach an IVR system when calling a service number, the customer may speak with a customer service representative (CSR) who either helps the customer or transfers the customer to an IVR. Within the IVR, the customer listens to one or more prerecorded menus or prompts and provides responses using either touch-tone input or speech input in order to accomplish their task. Therefore, the content and structure of the prerecorded menus or prompts needs to allow for a customer to easily and quickly accomplish their task with little frustration.

In order for IVR systems to meet customers' needs, the usability of IVR systems are tested and improved by conducting laboratory studies or tests where test participants are asked to accomplish sets of tasks using an IVR system. An example of a task to accomplish may be, “Call Telephone Company at 555-1111 and change your billing address.” In these studies or tests, the participants use telephones to interact with an IVR simulation application which is presented by a laboratory computer. The simulated IVR application plays prerecorded announcements or prompts to the participants in the form of a series of menus and records information regarding the participants' responses such as the menu name, the amount of time the prerecorded prompt played before the participant made a selection or pressed a key, and the key that the participant pressed. Once the study is completed, the recorded information regarding the participants' responses or the performance data is compiled into a log file with information regarding each task test stored as an individual performance data set.

To analyze the performance data collected by the IVR simulation application in the log file, the company may score participants call routing performance based on two factors—accomplishment of the task and the time spent in the IVR simulation application attempting to accomplish the task. Analysis of the log file and performance data is typically done as a manual process where one or more persons manually examine each performance data set noting the task, determining if the participant accomplished the task, and calculating the time spent listening to the menus or prompts and then manually creating an output file containing the findings of the IVR simulation. Given that a typical IVR study generally includes many participants each performing several different tasks, the manual analysis of the performance data is a very time consuming, labor intensive, and resource intensive process. In addition, the manual analysis of the performance data is also subject to human error such as math errors in calculating time spent in the menus and in omitting particular data points.

By contrast, the example embodiment described herein allows for the automated analysis of performance data. Additionally, the example embodiment allows for the consistent analysis of performance data free of human error. Time and money is saved because employees no longer manually examine the performance data determining if the task was accomplished,and manually calculating the time required to accomplish each task. Therefore, employees' time may be better utilized in other revenue generating projects since less time is required to analyze the performance data. Furthermore, the analysis of the performance data is more reliable because the analysis is not subject to human error such as calculation errors and different people are not interpreting the performance data in different manners.

Referring now to FIG. 1, a block diagram depicts analysis system 10 for automating the analysis of performance data. In the example embodiment, analysis system 10 may include respective software components and hardware components, such as processor 12, memory 14, input/output ports 16, hard disk drive (HDD) 18 containing database 20, and those components may work together via bus 24 to provide the desired functionality. The various hardware and software components may also be referred to as processing resources. Analysis system 10 may be a personal computer, a server, or any other appropriate computing device. Analysis system 10 may further include display 26 for presenting graphical user interface (GUI) 28 and input devices such as a mouse and a keyboard. Analysis system 10 also includes task engine 30 and score engine 32, which reside in memory such as hard disk drive 18 and are executable by processor 12 through bus 24. Display 26 presents GUI 28 which allows for the selection of the log files for analysis system 10 to automatically analyze and for the presentation of some of the analysis results. Shown in FIG. 1 is an example GUI 28 with GUI 28 illustrated in greater detail in FIG. 2. GUI 28 includes a plurality of screens and buttons that allow the user to access and control the operation of analysis system 10, task engine 30, and score engine 30.

Analysis system 10 allows for the automated analysis of one or more log files containing performance data and the generation of an output file including the results of the analysis on the performance data. Although the example embodiment is described in reference to IVR performance data, in alternate embodiments analysis system 10 may also automatically analyze performance data from other systems in addition to IVR systems as well as any other appropriate type of data.

FIG. 4 depicts a flow diagram of a method for the automated analysis of performance data. The method begins at step 110 and at step 112 a user of analysis system 10 selects the performance data to be analyzed. Analysis system 10 allows for up to three different log files to be analyzed at one time. In alternate embodiments, analysis system 10 may analyze more than three log files at the same time. Each time an IVR study or test occurs, a log file containing performance data from that test is created. So if there are three IVR tests in one day—one in the morning, one in the afternoon, and one in the evening—then there will be three log files at the end of the day. Analysis system 10 and GUI 28 allows for simultaneous analysis of the three log files at the same time to allow for more efficient operation of analysis system 10.

To analyze more than one log file at a time, the user selects the log file to be analyzed in input windows 34, 36, and 38. If only one log file is to be analyzed, the user selects the log file in input window 34. If more than one log file is to be analyzed, the first log file is selected in input window 34, the second log file is selected in input window 36, and the third log file is selected in input window 38. When selecting the log files to be analyzed, the user may also want to select the location to save the output file which can be done in output window 40.

Once the log files to be analyzed have been selected, the user presses process button 42 and analysis system 10 begins to automatically analyze the performance contained in the log file. At step 114, analysis system 10 selects the first performance data set in the log file to analyze. Analysis system 10 selects the performance data set to analyze by selecting the first the performance data set in the log file. A performance data set is the recorded data and information regarding one specific participant and one specific task for that participant. Generally in a IVR test, a participant is given four different tasks to accomplish such as “order DSL service” or “change your billing address.” For example, a performance data set would contain the recorded information for participant A and the task of ordering DSL service.

An example log file 60 including two example performance data sets 62 and 64 is shown in FIG. 3. A performance data set includes such information as the start time of the task, each menu accessed by the participant within the IVR, the time each menu was accessed, how long the participant listened to each menu, the key the participant pressed in response to the menu, and the total time the participant interacted with the IVR system.

Performance data sets are separated in a log file by start lines and end lines. Performance data set 62 includes start line 66 and end line 78 while performance data set 64 includes start line 80 and end line 92. Start lines 66 and 80 include the date of the IVR test, what IVR system is being tested, and the time that the first IVR menu begins to play. In start line 66, the date of the test is Apr. 5, 2002, the IVR system being tested is Yahoo2—Version B, and the first menu began playing at 8:23:53 AM. End lines 78 and 92 include total listening time 98 and 104 which is the total time that the participant spends listening to the menus and interacting with the IVR system. Performance data set 62 has total listening time 98 of 83 seconds and performance data set 64 has total listening time 104 of 64 seconds. Each line in-between start lines 66 and 80 and end lines 78 and 92 provides information regarding various submenus within the IVR accessed by the participant. For performance data set 62 and line 68, BMainMenu was accessed at 8:23:53 AM, the participant listed to BMainMenu for 30 seconds (listening time 96), pressed the “2” key (key 94), and BMainMenu stopped playing at 8:24:23 AM. Lines 70, 72, 74, and 76 supply the same type of information for each respective menu. Key 94 in line 76 is “TO” which indicates that the participant never made a selection in response to the “B22110” menu and therefore the participant was timed out of the menu.

Once analysis system 10 has selected the performance data set to be analyzed, task engine 30 determines a task code and task for the selected data set at step 116. The performance data sets do not contain a participant number identifying the participant or the task. But the participant number is stored in database 20 in a log-in call record file. When the participants access the IVR simulation application, analysis system 10 stores in database 20 each participant's participant number and the tasks they are to accomplish. Participants are generally given more than one task to accomplish and the participants are to attempt the tasks in a pre-specified order and the log files reflect this specified order of tasks. For example, if each participant is given four tasks to accomplish, then the log file includes four performance data sets for each participant where the four performance data sets for each participant are grouped together in the same sequence as the participant attempted each task. So if participant A was given the four tasks of “order DSL service,” “change your billing address,” “inquire about a bill payment,” and “add call-forwarding,” the log file has the four performance data sets for participant A one after the other in the same order as participant A was specified to attempt the tasks. Therefore, task engine 30 locates the participant number in database.20, determines what tasks the participant was supposed to accomplish and the order the tasks were to be accomplished, and determines which performance data sets correlate with which participants and tasks.

After task engine 30 determines the correct task for the selected performance data set, at step 118 task engine 30 retrieves from database 20 the correct key sequence for the corresponding task for the selected performance data set. Each task has a distinct correct key sequence so that for example that correct key sequence for “ordering DSL service” is different from the correct key sequence for “changing your billing address.” The correct key sequence is the keys pressed in response to the IVR menu prompts that allows the participant to navigate the IVR menus and successfully accomplish the assigned task. For instance, the task of “ordering DSL service” requires the participant to navigate through and listen to three different menus in order to order DSL service. After the first menu, the participant needs to press the “3” key which sends the participant to the second menu. After the second menu the participant needs to press the “2” key which sends the participant to the third menu. After the third menu the participant needs to press the “4” key after which the participant has ordered DSL service and successfully completed the task. Therefore the correct key sequence for the task of “order DSL service” is “3, 2, 4.”

At step 120, score engine 32, having the correct key sequence from task engine 30, searches the selected performance data set for the correct key sequence. Score engine 32 searches the last few keys 100 for the correct data sequence. Score engine 32 starts with the line right above end line 92 and begins searching up the lines 90, 88, 86, 84, and 82 to start line 80 looking for the correct key sequence. Score engine 32 examines the end of the selected performance data set because that is the only location where the correct key sequence may be located because when the participant enters the correct key sequence, the task is accomplished, the performance data set ends, and the participant moves on to the next assigned task. Therefore once the participant enters the last key of the correct key sequence, the next line in the performance data set is end line 92 and a new performance data set begins.

Score engine 32 compares the recorded key sequence entered by the participant with the correct key sequence at step 122. For example, performance data set 64 is for the task of “changing your billing address” and the task has a correct key sequence of “2, 2, 1, 1, 5.” Score engine 32 compares the correct key sequence with the recorded key sequence in performance data set 64 beginning with line 88 which has “5” as key 100. Score engine 32 then moves up to line 86 to look for “1” as key 100 and finds “1” as key 100. Score engine 32 repeats this process for lines 86, 84, and 82 until a line does not have the correct key 100 or until score engine 32 determines that the recorded key sequence of performance data set 64 is the same as the correct key sequence.

Once score engine 32 compares the correct key sequence with the recorded key sequence for the selected performance data set at step 122, at step 124 score engine 32 determines if the task for the selected performance data set was successfully accomplished. The task is successfully accomplished if the recorded key sequence includes the correct key sequence. The task is not successfully accomplished or is a failure if the recorded key sequence does not include the correct key sequence. If the task is not accomplished, then at step 126 score engine 32 marks the selected performance data set as a failure. If the task is successfully accomplished, then at step 128 score engine 32 marks the selected performance data set as a success or as passing. For example, performance data set 62 timed out (“TO”) in line 76 because the participant made no selection and therefore performance data set 62 cannot have the correct key sequence and score engine 32 marks performance data set 62 as failing. Determining whether the selected performance data set accomplished the task allows for an objective performance measure and provides a call-routing accuracy.

In addition to call-routing accuracy, analysis system 10 also provides for another objective performance measure—the amount of time the participant listens to each IVR menu and the total amount spent attempting to accomplish or accomplishing the assigned task. The amount of time the participant spends listening to the menu is not a very valuable number unless menu duration times are also taken into account. A menu duration time is the amount of time it takes for a menu to play in its entirety. For instance, a menu may have five different options to choose from and the menu duration time is the amount of time it takes for the menu to play through all five options.

At step 130, score engine 32 obtains the menu duration time from database 20 for the first menu in the selected performance data set. Score engine 32 also obtains the listening time for the first menu in the selected performance data set. The listening time is the time a participant actually spends listening to a menu before making a selection. For instance, performance data set 64 contains the first menu BMainMenu that has listening time 102 of 30 seconds (line 82). From database 20, score engine 32 retrieves that menu BMainMenu has a menu duration time of 30 seconds.

Once score engine 32 obtains both the listening time and the menu duration time, score engine 32 calculates the response time or the cumulative response time (CRT) for the first menu at step 132. The response time is the difference between the menu duration time and the listening time. Score engine 32 calculates the response time by subtracting the menu duration time from the listening time. For example, if the main menu of the IVR is 20 seconds in length, and the participant listens to the whole menu and then makes a selection, the participant has a listening time of 20 seconds and receive a CRT score or response time of 0 (20−20=0). If the participant only listens to part of a menu, hears their choice and chooses an option before the whole menu plays, then the participant receives a negative CRT score or response time. For instance, if the participant chooses option three 15 seconds (listening time) into a four-option, 20 second menu, the participant receives a CRT score or response time of “−5” (15−20=−5). Conversely, the participant has a response time of +15 if the participant were to repeat the menu after hearing it once, and then choose option three 15 seconds (35 second listening time) into the second playing of the menu (35−20=15). For performance data set 64 and line 82, the participant has a response time or CRT score of 0 because the participant has a listening time of 30 seconds and the BMainMenu menu has a menu duration time of 30 seconds (30−30=30).

After the calculation of the response time for the first menu, score engine 32 at step 134 determines if the selected performance data set has additional menus for which a response time needs to be calculated. If there are additional menus within the selected performance data set at step 134, then at step 136 score engine 32 obtains the menu duration time from database 20 for the next menu and the listening time for the next menu in the same manner as score engine 32 obtained the menu duration time and listening time for the first menu at step 130. So for performance,data set 64, score engine 32 obtains the menu duration time and listening time for line 84 and menu “B20.” Once score engine 32 obtains the menu duration time and the listening time for the next menu, at step 138 score engine 32 calculates the response time for the next menu in the same manner as described above at step 132. The method then returns to step 134 where score engine 32 determines if the selected performance data set has additional menus that have not yet been analyzed. Steps 134, 136, and 138 repeat until there are no additional menus to be analyzed within the selected performance data.

If there are no additional menus within the selected performance data set at step 134, then at step 140 score engine 32 calculates the total response time for the selected performance data set. The total response time is the difference between the total menu duration time and the total listening time. Score engine 32 calculates the total response time by first summing the menu duration times and the listening times for each menu within the selected performance data set. Once score engine 32 has both a total menu duration time and a total listening time, score engine 32 calculates the total response time for the selected performance data set by subtracting the total menu duration time from the total listening time. A negative total response time indicates that less time was used than required to accomplish the task, a zero response time indicates that the exact amount of time was used by the participant to accomplish the task, and a positive response time indicates that more time was used than required to accomplish the task. For instance, performance data set 64 has a total listening time 104 of 64 seconds and a total menu duration time of 75 seconds. Therefore, performance data set 64 has a total response time of −11 seconds (64−75=−11).

Once score engine 32 calculates the total response time for the selected performance data set, at step 142 analysis system 10 determines if there are additional performance data sets within the log file to be analyzed. If at step 142 there are additional performance data sets, then analysis system 10 selects the next performance data set at step 144 and the method returns to step 116 and repeats as described above until there are no additional performance data sets in the log file or files to be analyzed at step 142.

When there are no additional performance data sets to be analyzed at step 142, analysis system 10 and score engine 32 generate an output file at step 146 and the method ends at step 148. The output file is similar in structure to the log file and performance data and is sorted by participant and sequence of task. The output file includes all the information in the log file as well as additional information such as the participant number, the assigned task, the IVR system used by the participant, the response time for each menu, the total response time, and whether the task was successfully accomplished. The output file may also contain the correct key sequence for each performance data set. The output file allows a user of analysis system 10 to determine which IVR menu and tasks may need to be redesigned based on high positive response times or failures to accomplish tasks. For example, a performance data set for a particular task that was successfully accomplished but has very high response times may indicate that the menus need to be redesigned or reworded because although the participants accomplished the task, they had to listen to the menus several times before being able to make a selection.

In addition to the output file, GUI 28 has an additional feature that allows a user of analysis system 10 to quickly determine the reliability of IVR test results. Summary window 44 allows the user to quickly determine the pass/fail results for task accomplishment for each participant. Because participants may not take the IVR test seriously and others may only be taking the test to be paid, not all of the participants actually attempt to accomplish any of the assigned tasks. A participant intentionally failing all assigned tasks is not good for the overall test results and affects the analysis of the IVR system. A participant failing all of their assigned tasks is a good indication that the participant did not really try and that the associated performance data should be ignored when analyzing the output file. Summary window 44 allows the user to quickly peruse each participant's pass/fail results and call-routing accuracy without having to examine the output file and therefore determine which performance data should be disregarded and which tasks need to be tested again.

The call-routing and response time results of the IVR usability test yield important information that can be used in the further development and refinement of IVR systems. Based on these measures, companies can select IVR designs associated with the best objective performance and usability score and have an IVR system that is efficient and satisfactory to the customers.

Although the present invention has been described in detail, it should be understood that various changes, substitutions and alterations can be made hereto without the parting from the spirit and scope of the invention as defined by the appended claims. 

1. A graphical user interface (GUI) comprising: a first display area comprising a first user selectable object to permit selection of a first log file for analysis, the first log file comprising data associated with an interactive voice response (IVR) system simulation conducted using at least a first participant; a second display area comprising a second user selectable object to permit selection of a second log file for analysis, the second log file comprising data associated with an IVR system simulation conducted using at least a second participant; and at least a third display area to present participant-specific results associated with the analysis of at least one of the first log file and the second log file.
 2. The GUI of claim 1, wherein the participant-specific results comprise a pass/fail summary for the first participant and the second participant.
 3. The GUI of claim 1, further comprising a fourth display area comprising a third user selectable object to permit selection of an output file.
 4. The GUI of claim 1, further comprising at least one user selectable object selectable to initiate analysis of at least one of the first log file and the second log file.
 5. The GUI of claim 1, wherein the participant-specific results comprise information associated with performance of a correct key sequence.
 6. The GUI of claim 1, wherein the participant-specific results comprise information associated with participant response times.
 7. A method of presenting information associated with an interactive voice response (IVR) system test, the method comprising: displaying a first user selectable object on a graphical user interface (GUI), the first user selectable object selectable to permit a user to select a first log file for analysis, the first log file comprising data associated with an IVR system test conducted using at least a first participant; displaying a second user selectable object on the GUI, the second user selectable object selectable to permit a user to select a second log file for analysis, the second log file comprising data associated with an IVR system test conducted using at least a second participant; and displaying participant-specific results associated with the analysis of at least one of the first log file and the second log file in a results display area.
 8. The method of claim 7, further comprising displaying, on the GUI, a pass/fail summary for the first participant and the second participant.
 9. The method of claim 7, further comprising displaying, on the GUI, a third user selectable object, the third user selectable object selectable to permit selection of an output file.
 10. The method of claim 7, further comprising displaying, on the GUI, at least one user selectable object selectable to initiate analysis of at least one of the first log file and the second log file.
 11. The method of claim 7, wherein the participant-specific results comprise information associated with performance of a correct key sequence.
 12. The method of claim 7, wherein the participant-specific results comprise information associated with participant response times.
 13. A system comprising: means for retrieving a correct key sequence for a first task performed by a first participant as part of a first interactive voice response (IVR) system test; means for retrieving a correct key sequence for a second task performed by a second participant as part of a second IVR system test; means for scoring the performance of the first participant and the second participant; and a graphical user interface (GUI) comprising a first display area to present scoring results for the first and second participant.
 14. The system of claim 13, wherein the scoring results comprise a pass/fail summary for the first participant and the second participant.
 15. The system of claim 13, wherein the GUI comprises: a second display area comprising a first user selectable object to permit selection of a first log file for analysis, the first log file comprising data associated with an interactive voice response (IVR) system simulation conducted using the first participant; a third display area comprising a second user selectable object to permit selection of a second log file for analysis, the second log file comprising data associated with an IVR system simulation conducted using the second participant; and a fourth display area comprising a third user selectable object to permit selection of an output file.
 16. The system of claim 15, wherein the GUI further comprises a selectable object selectable to initiate analysis of at least one of the first log file and the second log file.
 17. The system of claim 13, wherein the means for scoring comprises: means for comparing the correct key sequence for the first task against an actual performance by the first participant; and means for comparing the correct key sequence for the second task against an actual performance by the second participant.
 18. The system of claim 17, wherein the scoring results comprise information associated with the actual performance of respective correct key sequences by the first participant and the second participant.
 19. The system of claim 13, wherein the means for scoring comprises: means for determining a response time of the first participant to perform the correct key sequence for the first task; and means for determining a response time of the second participant to perform the correct key sequence for the second task.
 20. The system of claim 19, wherein the scoring results comprise information associated with the response time of the first participant and the second participant. 